Threads Post Comments Scraper

Scrape replies and comments on Meta Threads posts by post ID or share URL. For each post the Actor returns the root post plus its replies as structured records: reply text, author username, like count, reply / repost / quote counts, timestamp, and the post URL.

Unofficial. This Actor is not affiliated with, authorized, or endorsed by Threads, Instagram, or Meta Platforms, Inc. It is an independent tool that retrieves publicly available data via a third-party API. Use it in compliance with Threads' / Meta's terms and all applicable laws; you are responsible for how you use the retrieved data.

What it does

• By post ID — give one or more Threads post IDs (the numeric pk, e.g. 3906263078447871896). For each ID the Actor fetches the post and pages through its replies. The first record per post is the root post; the rest are replies.
• By post URL — give Threads post / share URLs (e.g. https://www.threads.net/@zuck/post/DY11ZLWG_eY). Each URL is resolved to its post ID, then scraped the same way.

Input

Field	Type	Default	Description
postIds	string[]	["3906263078447871896"]	Threads post IDs (numeric pk) to scrape.
postUrls	string[]	[]	Threads post / share URLs; each is resolved to a post ID.
maxItems	integer	50	Max total records (root posts + replies) across all inputs.

Example input

{
  "postIds": ["3906263078447871896"],
  "postUrls": ["https://www.threads.net/@zuck/post/DY11ZLWG_eY"],
  "maxItems": 100
}

Output

One dataset item per record (root post or reply):

{
  "id": "3906578411389002392_63460956422",
  "postId": "3906578411389002392",
  "code": "DY29F4CDSKY",
  "url": "https://www.threads.net/@yannlecun/post/DY29F4CDSKY",
  "isRootPost": false,
  "text": "Awesome work by Alex and team!",
  "username": "yannlecun",
  "userId": "63460956422",
  "userFullName": "Yann LeCun",
  "isVerified": true,
  "userProfilePicUrl": "https://...",
  "likeCount": 192,
  "replyCount": 3,
  "repostCount": 0,
  "quoteCount": 0,
  "reshareCount": 0,
  "isReply": true,
  "takenAt": 1779920458,
  "source": "postId:3906263078447871896"
}

Notes

• Data is sourced live; Threads occasionally rate-limits, so the Actor retries transient blocks with exponential backoff.
• Records are de-duplicated by ID within a run, and replies are paged via the upstream end_cursor until exhausted or maxItems is reached.

Quick start

1. Open the Actor and press Run — the default input works out of the box.
2. Adjust the input fields below to your target (keywords, IDs, or URLs) and set maxItems to cap spend.
3. Grab results from the Dataset tab as JSON / CSV / Excel, or pull them via the Apify API and MCP from your own code.

No proxies to configure, no cookies to paste, no login — the Actor handles everything server-side.

Why teams switch to this Threads replies scraper

Replies are where Threads conversations actually happen, and they're what browser-based scrapers drop most often mid-run. This Actor walks a post's reply thread via a direct HTTP API and returns every reply with author and engagement data at $2.50 per 1,000 replies — reliably, with no login.

What people build with it

• Audience sentiment — what did people actually say under your launch post? Feed the replies to an LLM for a structured readout.
• Community management — collect replies across all your posts daily and triage questions that deserve answers.
• Campaign measurement — reply volume and tone are the engagement-quality metrics likes can't give you.
• UGC mining — testimonials and objections, verbatim, under any product conversation in your niche.
• Thread research — study how high-performing posts handle their replies to learn what keeps a thread alive.

Tips for better results

• Accepts post URLs straight from the Threads share button.
• Each reply includes the author handle — join with Threads User Posts to profile your most engaged commenters.
• Find conversation-heavy posts first with Threads Search.

---

Why this Actor

• Direct API, no headless browser — fast, stable runs with nothing to babysit.
• No login, no cookies — we never touch your accounts, so there's no ban risk.
• Fresh, real-time data — every run reads the source live, not a stale cache.
• Pay per result — you're billed only for the rows actually delivered.
• Structured JSON — export to CSV, Excel, or JSON, or pull straight from the API / MCP.

Use cases

• Mine audience sentiment and feature requests from real comment threads.
• Surface the most-liked replies and frequent questions under any post.
• Build moderation, UGC, or social-listening datasets at scale.
• Spot superfans and detractors by author and engagement.

FAQ

Do I need an account, cookies, or to log in anywhere? No. The Actor talks to a fast, direct HTTP API server-side — you just provide inputs and run it.

How am I billed? Pay-per-result: a fixed price per row returned, with no separate platform/compute charge. Caps like maxItems keep spend predictable.

Can I run it on a schedule or call it from my app? Yes — use Apify Schedules, the REST API, the JavaScript / Python clients, or the MCP server. See the API tab.

Is this affiliated with Threads? No. It's an independent tool that collects publicly available data. Use it in line with the platform's terms and applicable law.

More Threads scrapers by us

• Threads Search — Top & Recent posts by keyword
• Threads User Posts — Profile feed by username
• Threads Profile Search — Find users by keyword

Browse the full fleet → https://apify.com/ethereal_wool